fix(init): skip interactive prompts when --resume is passed (closes #2098) - #2147

Thanks @Larslllllll, and sorry for the collision: #2106 was opened against #2098 two days before this and is already through review, so that is the one I am going to land. Nothing wrong with your read of the bug, you landed on the same one-line gate.

Two differences worth knowing for next time, since neither is obvious from the issue. #2106 lifts the predicate out into a small _interactive_gate function with a case per flag, so the questionnaire cannot be re-opened by a later flag without a test going red; the inline and chain here has no such guard. And its notice avoids saying anything about how to suppress itself, which is the one thing I held that PR on: the print is unconditional under if resume:, so a line offering a way to silence it would be false in both versions.

If you want another one in the same area, #2137 is open and unassigned: editor_files: {vscode_mcp: false} is a key repowise writes and then never reads back, and the thread has the two gates that cause it. Say the word on that issue and it is yours.

I am leaving this open rather than closing it today: if #2106 goes quiet on the string change I asked for, yours is the fallback and I will merge it instead. Either way you will hear which on this thread.

@Larslllllll, #2098 is fixed and closed, by #2106. As I said when you opened this, that one arrived on the issue first and carried tests, so it was the one I wanted to land; it went in a few minutes ago. Closing this as a duplicate rather than leaving it sitting red.

To be fair to your version, it is the same one-line diagnosis and you got there independently on the same day. The thing #2106 adds is that it lifts the predicate out of the inline and chain into a named _interactive_gate with a case per flag, so the next option added to that condition arrives with a test saying what it does to a resume. That is the only difference that decided it, not correctness.

If you want another, #2137 is open, labelled help wanted and unassigned: editor_files: {vscode_mcp: false} is a key repowise writes to config.yaml and then never reads, so init and update rewrite .vscode/mcp.json regardless. It is two gates rather than one and the thread already sets out where they are, including the trap that claude_md defaults True while agents_md defaults False, so a generic loop has to disable only on an explicit False. Say the word on that thread and it is yours.

Correction to what I wrote above, @Larslllllll: I pointed you at #2137 without checking it properly, and it was already claimed. @z2Ace0107 asked for it on 5 September with a scoped plan and had simply been waiting on a reply from us; I have assigned it to them. That was my error, not a change of mind, and I am sorry for sending you at something that was not free.

Rather than hand you another one I have not checked, tell me roughly what you would like to work on, CLI, server, ingestion, or the web UI, and I will find you something genuinely unclaimed and confirm it is yours before you spend any time on it. You have now had two near-misses on this repo in one day and neither was your fault.